home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
ada
/
gnat1792.zip
/
gnat179b
/
readme.dj
< prev
next >
Wrap
Text File
|
1994-06-01
|
16KB
|
404 lines
This is the README file for DJ's GCC port to DOS ("djgpp")
Contents:
* Overview
* What's available
* How to install
* Deviations and Caveats
* Copyright information
Disclaimer: This software is distributed WITHOUT ANY WARRANTY; without
even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
DJ Delorie
USmail: 24 Kirsten Ave, Rochester, NH 03867-2954, USA
email: dj@ctron.com
mailing list: djgpp@sun.soe.clarkson.edu (listserv@sun.soe.clarkson.edu)
djgpp-announce@sun.soe.clarkson.edu (listserv@sun.soe.clarkson.edu)
(do not send add/delete messages to djgpp or djgpp-announce)
Overview:
This package contains a 32-bit 80386 DOS extender with symbolic
debugger, a C/C++ compiler with utilities, development libraries, and
source code. It generates full 32-bit programs and supports full
virtual memory with paging to disk.
Requirements:
A 80386-based IBM compatible PC or PS/2, 4Mb of hard drive space (70M
for full install), and 512K RAM. Available extended (or expanded under
VCPI) memory is strongly recommended.
Supported Wares:
* Up to 128M of extended memory (expanded under VCPI)
* Up to 128M of disk space used for swapping
* SuperVGA 256-color mode up to 1024x768
* 80387
* XMS & VDISK memory allocation strategies
* VCPI programs, such as QEMM, DESQview, and 386MAX
* DPMI programs, such as Windows 3.x, OS/2, and QDPMI
Unsupported:
* Multiprocessing (fork())
File location:
host: omnigate.clarkson.edu
login: ftp
password: send your e-mail address
directory: ~ftp/pub/msdos/djgpp
Many thanks to the sysops at Clarkson for providing a home to djgpp!
As a convenience to non-FTP users, djgpp is also stored on Clarkson's
archive server. To access the archive server, do this:
% mail archive-server@omnigate.clarkson.edu
Subject: <none>
help
index msdos/djgpp
^D
NOTE: In accordance with FSF CopyLeft, you are not allowed to upload
this program to a distribution site unless you upload the source modules
with any binary module you upload. Please read the file COPYING for
more details.
NOTE: If your application links in object modules that were written by
FSF, your application counts as a "derived work" and must obey the
provisions of the FSF Copyrights. See the file COPYING for details.
All FSF source-based libraries are in the file libgpl.a and libgpp.a.
The mere act of compiling does not affect the copyright status of your
program.
INSTALLING:
To install, you must do the following:
* Create a "temp" directory, like c:\tmp.
* Create a directory to install in, like c:\djgpp.
* Un-zip the appropriate zipfiles in the install directory.
C:\DJGPP> unzip -o djeoe111.zip (Minimum runtime stuff - required)
C:\DJGPP> unzip -o djdev111.zip (Minimum development stuff - required)
C:\DJGPP> unzip -o gcc257bn.zip (The C compiler - required)
C:\DJGPP> unzip -o gas211bn.zip (The assembler - required)
C:\DJGPP> unzip -o bnu22bn.zip (The linker etc - required)
C:\DJGPP> unzip -o djdoc111.zip (If you want documentation)
C:\DJGPP> unzip -o txi210bn.zip (If you want the online doc reader INFO.EXE)
C:\DJGPP> unzip -o gpp257.zip (If you want to compile C++)
C:\DJGPP> unzip -o objc257.zip (If you want to compile Objective-C)
C:\DJGPP> unzip -o bsn121bn.zip (If you want to use bison)
C:\DJGPP> unzip -o flx238bn.zip (If you want to use flex)
C:\DJGPP> unzip -o gzp124bn.zip (If you want gzip)
C:\DJGPP> unzip -o zip50bn.zip (If you want zip and unzip)
C:\DJGPP> unzip -o dj111m1.zip (Maintainence releases)
The maintainance releases are numbered dj111m1.zip, dj111m2.zip, etc.
Install them all, in order, after all other modules.
If you prefer to use pkunzip, use "pkunzip -d -o" instead of "unzip -o".
Note: The file "unzip-dj.exe" is available from where you got djgpp.
It is Info-Zip's unzip v5.0 built with djgpp, and includes a built-in
copy of go32.exe.
Other .zip files contain various documentation (*dc.zip) and source
files (*sr.zip, *s1.zip, etc).
* If you are installing over an existing djgpp area, make sure you remove
the files bin/aout2exe.exe and bin/exe2aout.exe. They have been replaced
with coff2exe and exe2coff. Also, some programs may not work correctly
if using an old version of go32 and/or an old emu387, so be sure to remove
any old versions of these files.
* Add the following lines to C:\CONFIG.SYS file (or edit existing
files= and shell= lines as appropriate). The files= line prevents "too many
open files" errors when compiling, and the shell= line prevents "Out of
environment space" errors when setting lots of environment variables.
files=15
shell=c:\command.com c:\ /e:1000 /p
The values 15 and 1000 are close to minimal. You may want to increase them
to provide a little more margin.
* Add the following lines to C:\AUTOEXEC.BAT:
call c:\djgpp\bin\setdjgpp c:\djgpp c:/djgpp
(note the use of '\' in the first option and '/' in the second)
* Optionally, add these lines to override the defaults set by setdjgpp:
set TMPDIR=c:/tmp
^^^ this is where gcc's temp files go. It should be a ramdrive
if you have one.
set GO32TMP=c:/tmp
^^^ this is where your paging file goes - if not set, the
variables TMP and TEMP are checked in that order. This
should be a real drive.
set GO32=driver c:/djgpp/drivers/SOMETHING.grd gw 1024 gh 768
^^^ whatever driver works with your VGA (optional)
Remember that unless you manually type these at the command line,
they won't take effect until you reboot. Don't include the "ansi"
keyword in the "go32" variable if you don't have an ANSI.SYS driver
or equivalent.
* Add your binaries directory to your PATH in C:\AUTOEXEC.BAT
SET PATH= . . . ;c:\djgpp\bin
That's it! djgpp is now installed on your system.
To try it out, change into the samples/hello directory of the DJGPP
distribution and type "tryit". If this doesn't work, run "testit",
which will check things out for you.
Note: For some operating systems, such as OS/2 and NT, you may need to
use the 16-bit gcc driver instead of the 32-bit gcc driver. To do so,
copy the gcc.exe file from utils/gcc-rm/gcc.exe to bin/gcc.exe.
Don't forget to save the old gcc.exe first!
The GO32 environment variable:
This variable controls the options available in go32. The syntax of
this variable is:
SET GO32=[parm [value]] [parm [value]] . . .
Parameters:
ansi Use ANSI commands to control the color in edebug32
mono Use the Monochrome monitor for debugging - useful when
debugging graphics applications
topline Display status information on the top line of the screen
(or the top of the mono monitor)
1rm Redirect stdout (file #1) to the monochrome monitor
2rm Redirect stderr (file #2) to the monochrome monitor
1r2 Redirect stdout (file #1) to stderr (file #2)
2r1 Redirect stderr (file #2) to stdout (file #1)
nodpmi don't use dpmi even if you find it.
core [file] append exception traceback to the named file.
glob enable globbing (default)
noglob disable globbing
emu [path] Use the specified file as the 80387 emulator
driver [path] Use the specified file as the graphics driver
gw [width] Default graphics width
gh [height] Default graphics height
tw [width] Default text width
th [height] Default text height
nc [colors] Number of colors (for new-style drivers only - see cbgrx*.zip)
These parameters may occur in any order.
Note that "1rm" and "2rm" are done before "1r2" and "2r1", so "1rm 2r1" sends
stdout to the mono monitor and stderr to any redirection used.
Examples:
C:\> set GO32=mono driver c:\dj